feat: emit lockup_violation event on transfer revert (Closes #587) - #692

Overview

Attempts to transfer locked-up shares now revert cleanly and emit a structured lockup_violation event with the attempted amount, caller address, and current unlock schedule for indexer alerting.

Related Issue

Closes #587

Changes

• [ADD] EVENT_LOCKUP_VIOLATION constant — topic: lock_viol
• [ADD] LockupViolation = 63 error variant to RevoraError enum
• [ADD] Lockup check in transfer_with_attestation: rejects transfer when unlocked_bps < 10,000
• [ADD] Event emission: (EVENT_LOCKUP_VIOLATION, from) -> (to, amount_bps, schedule) on violation

Security

• Transfer reverts cleanly with no state mutation on lockup violation
• Event includes caller address and full schedule for indexer alerting
• No bypass: check runs on every transfer via transfer_with_attestation
• Edge cases: transfer at exactly unlock_ts is allowed (unlocked_bps == 10,000)

Verification

cargo test --all